subsidiary plans
plan
Resource plan
Stakeholders
Project Deliverables
Requirements & constraints
Project benefits
Scope statement
WBS
Work packages
Duration
Cost
Network diagram
Risk register
Risk responses
Communication plan
PMBOK Guide (6thEd) Part 2, Sec. 1.9 Table 1-1
Risk(Part 1, Sec 11)
Scope (Part 1, Sec. 5)
Schedule(Part 1, Sec. 6)
Cost(Part 1, Sec. 7)
Stakeholders
(Part 1, Sec. 13)
Communications
(Part 1, Sec. 10)
Resources
(Part 1, Sec.9)
1
Black, K. (1996). Causes of project failure: a survey of professional engineers.PM Network, 10(11), 21–24.
Collect requirements
GSOE9820 Engineering Project Management
Imrana Kabir
PMBOK Guide (6thEd) Part 1, Sec. 5.2
Dwivedi, N. “Elicitation Techniques” video in course Software Design: Developing effective requirements, accessed 23/02/2021, LinkedIn Learning accessed through UNSW
How about an agile specification? User stories!
A user story is an informal, general explanation of a feature written from the perspective of the end user.
Sydney Harbourforeshore authority
Pyrmont bridge
Reference: NSW Government, The Star Group
Pyrmont bridge
Requirements Method: Document analysis
Reviewed Roads and Maritime Services (RMS) report on existing conditions (e.g. traffic and transport use)
Identified:
Reference: Pyrmont Master Plan, Traffic and Transport, December 2005
Writing great requirements simplifies testing and configuration management!
Functional requirement:describes behaviour of the product by actions, processes…
Non-functional requirement:qualities/conditions for product to be effective
(PMBOK 5.3.2)
Inspired by 1.5.1. Department of Transport and Main Roads, Queensland
Define scope
GSOE9820 Engineering Project Management
Imrana Kabir
Scope definition is the creative center of project management
Requirements
Constraints
Project priorities
Scope statements and WBS
‘The problem’
‘The solution’
Develop project scope
PMBOK Guide (6thEd) Part 1, Sec. 3.4.3
The bad
The good ☺
But, what if you only partly know all the requirements and the scope at the beginning?
(surprisingly, common situation)
Triple constraint
GSOE9820 Engineering Project Management
Imrana kabir
The WBS
GSOE9820 Engineering Project Management
Imrana Kabir
From: Project Management Institute, Practice Standard for Work Breakdown Structures (Project Management Institute, 2nd ed., 2006)
PMBOK Guide (6thEd) Part 1, Sec. 5.4.1
Rogers, J. “Work breakdown structure” video in course Construction Management, Planning and Scheduling, accessed 23/02/2021, LinkedIn Learning accessed through UNSW
This video gives a nice explanation of how the WBS includes more than just the PBS, and how it is not about scheduling, and the presenterdefines the work packages correctly.
1
PMBOK Guide (6thEd) Part 1, Sec. 5.4.2
PMBOK Guide (6thEd) Part 1, Sec. 5.4.2
1
1
“The NSW Government is working towards achieving a target of net-zero emissions by 2050. Transport for NSW has responded accordingly and will attempt to transition the NSW bus fleet to net zero by 2030.”
Disclaimer: these statements are not perfect and are not guaranteed 100%!
Disclaimer: these statements are not perfect and are not guaranteed 100%!
Is each sub-deliverable small enough for 1 person to be responsible?
Disclaimer: this WBS is not perfect and are not guaranteed 100%!
Is the WBS Coding correct?
Formulating WBS in different PM lifecycles
GSOE9820 Engineering Project Management
Imrana Kabir
Concept
Characteristics
Agile Practice Guide (2017) Sec. 3.1.1
Concept
Characteristics
Agile Practice Guide (2017) Sec. 3.1.2
Concept
Example:
Characteristics
Agile Practice Guide (2017) Sec. 3.1.3
Straçusser, G. (2015). Agile project management concepts applied to construction and other non-IT fields. Paper presented at PMI® Global Congress 2015—North America, Orlando, FL. Newtown Square, PA: Project Management Institute.
The 100% ‘Agile’ PM model works best with few interdependencies between most of the work packages
Focused on continuous releases that incorporate customer feedback, which can be more suitable for modern businesses with rapid responses/change
Agile Practice Guide (2017) Sec. 3.1.
subsidiary plans
plan
Resource plan
Stakeholders
Project Deliverables
Requirements & constraints
Project benefits
Scope statement
WBS
Work packages
Duration
Cost
Network diagram
Risk register
Risk responses
Communication plan
PMBOK Guide (6thEd) Part 2, Sec. 1.9 Table 1-1
Risk(Part 1, Sec 11)
Scope (Part 1, Sec. 5)
Schedule(Part 1, Sec. 6)
Cost(Part 1, Sec. 7)
Stakeholders
(Part 1, Sec. 13)
Communications
(Part 1, Sec. 10)
Resources
(Part 1, Sec.9)